Universal transponder

ABSTRACT

An account is managed using information read from a dual frequency transponder. Information stored on the dual frequency transponder can be read by a NFC-enabled device and by a UHF RFID reader. The information links, corresponds, or otherwise provides access to account information stored at a remote server. For example, a NFC-enabled device can read the information from the dual frequency transponder and use that information to enable instant and on-the-spot recharging of a toll account. In addition, a UHF RFID toll reader can scan information from the dual frequency transponder and use that information to debit toll charges from the correct toll account. The dual frequency transponder can be embedded in a license plate and read using a reader placed in the road. Additionally, the transponder can be configured to function at the correct frequency only when a valid vehicle registration sticker is applied to the license plate.

RELATED APPLICATION INFORMATION

This patent application is a continuation of co-pending U.S. patentapplication Ser. No. 14/684,289, entitled “UNIVERSAL TRANSPONDER,” filedApr. 10, 2015, which is a continuation-in-part of U.S. patentapplication Ser. No. 14/459,299, entitled “SYSTEMS AND METHODS FORMANAGING AN ACCOUNT,” filed on Aug. 13, 2014, now U.S. Pat. No.9,355,398, which claims the benefit under 35 U.S.C. § 119(e) to U.S.Provisional Application No. 61/865,600, filed Aug. 13, 2013, each ofwhich is incorporated herein by reference in its entirety. This patentapplication is a continuation of co-pending U.S. patent application Ser.No. 14/684,289, entitled “UNIVERSAL TRANSPONDER,” filed Apr. 10, 2015,which also claims the benefit under 35 U.S.C. § 119(e) to U.S.Provisional Application No. 61/978,167, filed Apr. 10, 2014, which isalso incorporated herein by reference in its entirety.

BACKGROUND 1. Technical Field

The embodiments described herein are related to Radio FrequencyIdentification (RFID) Applications, and more specifically toapplications that allow for improved management and recharging ofprepaid accounts.

2. Related Art

RFID is a technology that allows companies to develop applications in avariety of areas. At its core, RFID is a technology that allows for theidentification of objects or people and to communicate informationrelated to associated objects or people. Some of the major areas thatRFID is enabling new applications include asset tracking, companies canput RFID tags on assets that are lost or stolen often, that areunderutilized or that are just hard to locate at the time they areneeded; manufacturing, RFID has been used in manufacturing plants formore than a decade. It's used to track parts and work in process and toreduce defects, increase throughput and manage the production ofdifferent versions of the same product; supply chain management, RFIDtechnology has been used in closed loop supply chains or to automateparts of the supply chain within a company's control for years; paymentsystems, one of the most popular uses of RFID today is to pay for roadtolls without stopping; and security and access control, RFID has longbeen used as an electronic key to control who has access to officebuildings or areas within office buildings. There are also numerousother types of applications such as animal or human tracking andidentification, electronic passports, border crossing, libraryapplications,

An RFID system comprises one or more tags or transponders that aresomehow associated with an object or objects, and one or more readers orinterrogators configured to read information out of the tag. The readerreads information by broadcasting a Radio Frequency (RF) signal overcertain range. When a tag is within range of the reader and receives thesignal, it can reflect that signal back to the reader in order tocommunicate with the reader. In order to communicate, the reader may putcertain commands on the RF signal, and the tag can respond by puttinginformation stored in the tag onto the signal that is reflected back tothe reader.

RFID systems can employ various types of technology including activetechnology, semi-active technology and passive technology. Active andsemi-active systems include a battery within the tag. In passivesystems, no battery is included in the tag. Rather, the tag receives allthe energy it needs from the received RF signal. Because passive tags donot include a battery, they can be made smaller, are less expensive thanactive or semi-active tags, and can also provide much more flexibilityto design tags to meet various application and environmentalrequirements. While passive tags typically cannot communicate over aslong a distance, the size, cost, and flexibility provided by passivetags make them much more attractive for many applications.

RFID systems can also operate over many frequency ranges and inaccordance with several communication protocols. A couple of the mostcommon frequency ranges are the High Frequency (HF) band (13.56 MHz) andUltra-High Frequency (UHF) band (865-928 MHz). HF systems can operateover shorter ranges, e.g., 10 cm-1 m, and at lower data rates, whereasthe UHF systems can operate over longer ranges 1-12 m, and at higherdata rates.

Near Field Communication (NFC) systems are examples of HF systems. NFCis a set of standards for smartphones and similar devices to establishradio communication with each other by touching them together orbringing them into proximity, usually no more than a few inches. Presentand anticipated applications include contactless transactions, dataexchange, and simplified setup of more complex communications such asWi-Fi. Communication is also possible between an NFC device and anunpowered NFC chip in a tag.

NFC standards cover communications protocols and data exchange formats,and are based on existing radio-frequency identification (RFID)standards including ISO/IEC 14443 and FeliCa. The standards includeISO/IEC 18092[4] and those defined by the NFC Forum, which was foundedin 2004 by Nokia, Philips and Sony, and now has more than 160 members.The Forum also promotes NFC and certifies device compliance. It fits thecriteria for being considered a personal area network.

NFC builds upon RFID systems by allowing two-way communication betweenendpoints, where earlier systems such as contact-less smartcards wereone-way only. NFC devices can also be used in contactless paymentsystems, similar to those currently used in credit cards and electronicticket smartcards, and allow mobile payment to replace or supplementthese systems. For example, Google Wallet allows consumers to storecredit card and store loyalty card information in a virtual wallet andthen use an NFC-enabled device at terminals that accepts, for example,MasterCard PayPass transactions. The NFC Forum also promotes thepotential for NFC-enabled devices to act as electronic identitydocuments and keycards. As NFC has a shorter range and supportsencryption, it is generally better suited than earlier, less privateRFID systems for exchanging sensitive data such as personal finance andidentification.

While there are many uses for HF technologies such as NFC, UHFtechnologies typically support longer range communication and higherdata rates. Thus, UHF technology tends to excel in applications thatinclude but is not limited to tolling and electronic vehicleregistration, asset supervision, and supply chain management.

SUMMARY

A RFID system comprising a dual frequency RFID transponder.

These and other features, aspects, and embodiments are described belowin the section entitled “Detailed Description.”

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and embodiments are described in conjunction with theattached drawings, in which:

FIG. 1A illustrates an embodiment of a system in which an account ismanaged;

FIG. 1B illustrates an embodiment of a process in which an account ismanaged;

FIG. 2 illustrates an embodiment of a process for replenishing anaccount using a virtual wallet;

FIG. 3 illustrates an embodiment of a system in which an account ismanaged;

FIG. 4 illustrates an embodiment of a transponder used to manage anaccount;

FIG. 5 illustrates an embodiment of a UHF system;

FIG. 6 illustrates an embodiment of a HF system;

FIG. 7A illustrates the top view of an embodiment of a RFID-enabledlicense plate;

FIG. 7B illustrates the top view of an embodiment of a RFID-enabledlicense plate;

FIG. 7C illustrates the top view of an embodiment of a RFID-enabledlicense plate;

FIG. 8 illustrates the top view of an embodiment of a RFID-enabledlicense plate;

FIG. 9 illustrates an embodiment of a vehicle registration sticker thatis used in conjunction with a RFID-enabled license plate;

FIG. 10 illustrates an embodiment of the placement of a reader withrespect to a RFID-enabled license plate; and

FIG. 11 illustrates an embodiment of a universal transponder.

DETAILED DESCRIPTION

The embodiments disclosed herein can be implemented in numerous ways,including as a process; an apparatus; a system; a composition of matter;a computer program product embodied on a computer readable storagemedium; and/or a processor, such as a processor configured to executeinstructions stored on and/or provided by a memory coupled to theprocessor. In this specification, these example embodiments, or anyother implementations, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered. Unless statedotherwise, a component such as a processor or a memory described asbeing configured to perform a task may be implemented as a generalcomponent that is temporarily configured to perform the task at a giventime or a specific component that is manufactured to perform the task.As used herein, the term ‘processor’ refers to one or more devices,circuits, and/or processing cores configured to process data, such ascomputer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of operation. The invention is described in connection withsuch embodiments, but the invention is not limited to any embodiment.The scope of the invention is limited only by the claims and theinvention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Various embodiments of the systems and methods described herein aredirected toward applications for a multi-frequency transponder. Inparticular, the various embodiments of the systems and methods describedherein are directed toward applications for a dual frequency transponderthat incorporates both UHF and HF capabilities, and is therefore able tooperate over both the UHF band (e.g., 865-928 MHz) and the HF band(e.g., 13.56 MHz).

U.S. Provisional Patent Application Ser. No. 61/811,649, entitled‘Systems and Methods for Connecting People with Product Information,”filed Apr. 12, 2013, describes one application for a dual frequencytransponder. Meanwhile, the various embodiments of the systems andmethods described herein are directed toward applying the dual frequencytransponder to streamline electronic prepayment routines and practices.In particular, in various embodiments, a dual frequency transponder isused to enable immediate and on-the-spot prepayment of road tollsenforced through Electronic Toll Collection (ETC) systems. Althoughembodiments of the systems and methods described herein are with respectto applications for a dual frequency transponder in electronic tollcollection, it is to be understood that there are numerous otherpossible applications of a dual frequency transponder. For example,other applications for a dual frequency transponder include but are notlimited to parking access, customs and border control, and electronicvehicle registration (EVR).

ETC systems eliminate traffic delays on toll roads by automating tollcollection and obviating protracted stops at manual toll booths.Although a few ETC systems allows toll charges to be postpaid (i.e.,billed to users periodically and/or a later date), by far the mostcommon ETC billing mechanism is to automatically deduct the toll chargesfrom prepaid debit accounts. Generally, an ETC system must firstidentify a passing vehicle before it can electronically debit theaccount of registered vehicle owner. For vehicle identification, mostETC systems operating today (e.g., E-ZPass®) rely on RFID technology.More specifically, most ETC systems issue RFID transponders or tags thatare then registered or activated to link to specific vehicle owneraccounts. For instance, in order for a user, Alice, to gain access to anETC service, she will initially have to set up a toll account with anappropriate transit or toll authority (e.g., FasTrak® in the SanFrancisco Bay Area), and then carry a registered or activated RFIDtransponder in or on her vehicle. Meanwhile, most toll plazas have RFIDreader equipment installed on at least some toll gates. As Alice'svehicle passes through a toll gate on the San Francisco-Oakland BayBridge, the onboard FasTrak® transponder communicates to a RFID tollreader a unique radio signature identifying the vehicle. Based on thisunique radio signature, the ETC system can then determine the account(i.e., Alice's) from which to deduct the amount of the toll.

Some prepaid toll accounts are set up to be automatically replenishedwhenever the balance falls below a certain threshold. For example, ifAlice subscribes to a FasTrac® credit card account, a replenishmentamount equaling her average monthly usage (determined based on theprevious 90 days of use) is charged to the credit card linked to theaccount whenever the account's balance falls below a threshold of $15.Most users, however, wants autonomy over their prepaid toll accountbalances and would prefer to recharge their prepaid toll account attheir own discretion. Control over when and how much to recharge a tollaccount is especially attractive to users who incur toll charges on aninfrequent, intermittent, or irregular basis.

Nevertheless, current technology still imposes drastic limitations onwhen and where users can recharge prepaid toll accounts. Generally,recharging can only be performed at designated Point of Sale (POS)stations (e.g., convenient store, ATM). As such, users are required totake a number of proactive measures (e.g., check toll account status orbalance, find a POS station) well in advance of crossing a toll roadsince recharging cannot be done instantaneously and on-the-spot. Inpractice, many users will fail to check their account balance beforehandand won't realize that their account balance is insufficient until theyare at or near a toll gate where, absent any POS stations, they mustthen resort to time consuming manual toll transactions.

One primary reason why current technology falls short is that theconventional toll transponders in use today are single frequencydevices. The E-ZPass® transponder, for instance, operate over only asingle UHF (i.e., 915 MHz) band. Conventional toll transponders aredesigned to communicate only with the UHF RFID readers at toll gates.Consequently, only UHF RFID toll readers can gain access to theinformation stored on conventional toll tags. In contrast, the variousembodiments of the systems and methods described herein are directedtoward a dual frequency transponder. In various embodiments, Near FieldCommunication (NFC) technology is integrated with a UHF transponder. Theresulting dual frequency transponder, in various embodiments, is capableof communicating with NFC-enabled devices as well as UHF RFID readers.In various embodiments, when implemented as a toll transponder for usein an ETC system, the dual frequency transponder can communicate withboth a user's NFC-enabled device (e.g., smartphone) and the typical UHFRFID reader equipment found at toll gates.

Since Nokia introduced the first NFC-enabled phone in 2006, a steadystream of phones with NFC capabilities (e.g., Samsung Nexus™, MotorolaDroid) have been marketed and sold. As a result, a growing number ofusers have a portable NFC reader constantly ready at their disposal. AnNFC-enabled smartphone is equipped with an embedded NFC reader modulethat can communicate with other NFC devices, including but not limitedto other NFC-enabled smartphones, NFC POS terminals, and NFCtransponders and tags. Unlike other wireless technologies such asBluetooth®, which generally require manual device discovery and/orpairing, two NFC devices can detect and automatically initiate aconnection with one another as soon as they are within range (e.g., 4 cmor less). For example, an unlocked Google Android® smartphone will scanfor NFC tags, analyze any discovered NFC tags, categorize data from theNFC tags, and then launch the appropriate application(s) to handle eachNFC tag.

Prepaid Account Recharging Solution

FIG. 1A illustrates an embodiment of a System 100 in which an account ismanaged. According to FIG. 1A, System 100 includes a Transponder 110. Invarious embodiments, Transponder 110 is a dual frequency transponderthat communicates with Device 120 and Reader 130 using differentfrequency bands. In some embodiments, Transponder 110 is a dualfrequency transponder that can operate over both the HF and UHF band. Aswill be described in more detail below, in some embodiments, Transponder110 can be embedded, integrated, or otherwise included in a vehiclelicense plate. However, it is to be understood that multiple otherembodiments of Transponder 110 are possible, including but not limitedto a sticker (e.g., a self-adhesive decal that can be placed on anautomobile window, windshield, or license plate), a clamshell card, andan encapsulated device (e.g., in the housing of a rear-view mirror,headlights or taillights, the vehicle's front or rear bumpers, or in anynon-conductive component of the vehicle). In some embodiments,Transponder 110 is an active or semi-active device that relies on abuilt-in power source (e.g., batteries) to transmit its signals. Inother embodiments, Transponder 110 is a passive device that collectsenergy from interrogating signals from Device 120 and Reader 130.

As shown in FIG. 1A, in various embodiments, Transponder 110communicates with Device 120. In various embodiments, Device 120 is aNFC-enabled device (e.g., Android® smartphone) and Transponder 110communicates with Device 120 using the HF band. Meanwhile, in variousembodiments, Transponder 110 also communicates with Reader 130. Invarious embodiments, Reader 130 is a UHF RFID reader device andTransponder 110 communicates with Reader 130 using the UFH band. Inparticular, in various embodiments, Reader 130 can be a type of RFIDreader device that is typically installed at an electronic toll gate.However, as will be described in more detail below, in embodiments whereTransponder 110 is integrated, embedded, or otherwise included in alicense plate, Reader 130 is preferably placed in the road, underneathpassing vehicles as opposed to in an overhead gantry.

In various embodiments, Device 120 communicates with Transponder 110 inorder to manage a toll account, and to recharge the toll accountinstantaneously and on-the-spot. As shown in FIG. 1A, Application 121 isinstalled on Device 120. In various embodiments, physical interactionsbetween Transponder 110 and Device 120 triggers or activates Application121. For example, in one embodiment, touching or tapping Transponder 110and Device 120 together immediately opens Application 121 on Device 120.Alternately, in some embodiments, Application 121 opens immediately whenDevice 120 is brought within close proximity of Transponder 110. Invarious embodiments, physical interactions between Transponder 110 andDevice 120 further allow Device 120 to scan, read, or otherwise retrieveinformation stored on Transponder 110. For example, in one embodiment,by touching, tapping, or otherwise positioning Transponder 110 andDevice 120 together, Device 120 is able to read the information that isstored on Transponder 110. In various embodiments, Device 120 determinesto launch Application 121 automatically based on at least some of theinformation read from Transponder 110. In some embodiments, instead ofgaining access to all of the information stored on Transponder 110 atonce, physical interaction between Device 120 and Transponder 110 willinitiate an authentication process. In some embodiments, before Device120 is able to access, for example, prepaid toll account information, auser must provide the proper credentials (e.g., biometrics, username,password).

In various embodiments, at least some of the information stored onTransponder 110 can identify, link, or otherwise provide access to acorresponding prepaid toll account. As will be described in more detailbelow, in various embodiments, Application 121 is able to use at leastsome of the information read from Transponder 110 to obtain informationassociated with the toll account, including but not limited to accountstatus and account balance. As shown in FIG. 1A, Application 121communicates with ETC Server 170 over Network 140. In variousembodiments, Network 140 comprises one or more of a wired network, awireless network, a local area network, a wide area network, theInternet, or any other appropriate network. In some embodiments,Application 121 uses web or application services provided by ETC Server170 in order to obtain prepaid toll account information such as accountstatus and balance. Thus, in some embodiments, by activating Application121 through physical interactions between Transponder 110 and Device 120(e.g., touch, tap), a user can gain immediate access to latest prepaidtoll account information (e.g., status, balance).

In various embodiments, Application 121 additionally provides a userinterface for recharging a toll account. For instance, in someembodiments, Application 121 provides one or more GUI components (e.g.,text areas or fields, radio buttons, checkboxes, drop-down menu)allowing a user to select or to input, for example, an recharge amount,a payment method (e.g., a credit card selection), and security orauthentication credentials for the virtual wallet. In variousembodiments, Application 121 is integrated with a virtual wallet (e.g.,Google Wallet™) feature on Device 120. As will be described in moredetail below, in various embodiments, Application 121 interacts with thevirtual wallet (e.g., Google Wallet™) to replenish the user's prepaidtoll account.

As shown in FIG. 1A, in various embodiments, in addition to ETC Server170, Application 121 also communicates with both E-Wallet Server 150 andPayment Processor Server 160 over Network 140. In some embodiments,Application 121 requests payment information (e.g., a credit cardnumber) from E-Wallet Server 150 so that it can then request PaymentProcessor Server 160 to submit an appropriate recharge amount to ETCServer 170 to replenish the user's prepaid toll account. Advantageously,in various embodiments, the systems and the methods described hereinenable prepaid toll accounts to be managed and replenishedinstantaneously and on-the-spot. For instance, in various embodiments, auser is no longer required to seek out a POS station but can insteadrecharge his or her prepaid toll account while on the road and frominside the vehicle.

In various embodiments, Transponder 110 also communicates with Reader130. In various embodiments, Reader 130 comprises a UHF RFID reader thatis capable of reading information stored on Transponder 110 using theUHF (865-928 MHz) band. As shown in FIG. 1A, in various embodiments,Reader 130 is a RFID reader installed at a toll gate. Furthermore, asFIG. 1A shows, Reader 130 communicates with ETC Server 170 over Network140. In some embodiments, information that Reader 130 reads fromTransponder 110 is transmitted to ETC Server 170 via Network 140. Aswill be described in more detail below, in various embodiments,information stored on Transponder 110 can link, correspond, or otherwiseprovide access to other information, such as information that is storedelsewhere and remotely on a network server. For example, in variousembodiments, ETC Server 170 uses the information from Transponder 110 toidentify the vehicle and to apply a toll charge to the correct account.

FIG. 1B illustrates an embodiment of a Process 100 in which an accountis managed. In various embodiments, Process 100 is performed as a resultof physical interactions between Transponder 110 and Device 120described with respect to FIG. 1A.

At 102, at least some of the information stored on a dual-frequencytransponder is accessed. For example, as described with respect to FIG.1A, a NFC-enabled device such as Device 120 (e.g., Android® smartphone)is able to read the information stored on Transponder 110. In someembodiments, at last some of the information read from Transponder 110triggers the launch of Application 121 on Device 120. In addition, a UHFRFID toll reader such as Reader 130 is also able to read the informationstored on Transponder 110.

At 104, account information is accessed based on the information storedon the dual-frequency transponder. In various embodiments, at least someof the information stored on Transponder 110 links, corresponds, orotherwise provides access to account information. In variousembodiments, the information stored on Transponder 110 links,corresponds, or otherwise provides access to account information that isstored at a remote server. In some embodiments, the information storedat the remote server includes prepaid toll account information includingbut not limited to account status and balance.

At 106, at least one action is performed with respect to the account.For example, in some embodiments, action includes communicating theaccount information stored at the remote server (e.g., account status,account balance) to a user of Device 120 via Application 121. As anotherexample a type of action that can be performed with respect to theaccount, the user of Device 120 can also use Application 121 to rechargethe toll account. As will be described in more detail below, the user ofDevice 120 can replenish the toll account through a virtual wallet thatis integrated with Application 121. Finally, in some embodiments, a UHFRFID toll reader is also able to read the information stored onTransponder 110. In various embodiments, the UHF RFID toll reader can beconfigured to provide some or all of this information to a ETC system.In various embodiments, based on information scanned from thedual-frequency transponder by the UHF RFID toll reader, the ETC systemcan determine the account from which to deduct a toll charge.

Recharging with a Virtual Wallet

As described earlier with respect to FIG. 1A, various embodiments of thesystems and methods described herein simplify and abbreviate the processto recharge a toll account. For instance, in various embodiments, therecharging process can be initiated by simply bringing an NFC-enableddevice (e.g., Device 120) within the range of a dual frequencytransponder (e.g., Transponder 110). In response, in variousembodiments, the NFC-enabled device (e.g., Device 120) immediatelylaunches an application (e.g., Application 121) that is integrated witha virtual wallet (e.g., Google Wallet™). Otherwise stated, in variousembodiments, scanning a dual frequency toll transponder with aNFC-enabled device triggers an application that is configured tointeract directly with the virtual wallet. In various embodiments, theapplication provides a user interface for a user to select or inputvarious options (e.g., amount, credit card, credentials) to recharge atoll account. At the same time, in various embodiments, functions andfeatures of the virtual wallet are integrated into the application usingone or more appropriate Application Programming Interfaces (APIs). Forexample, to enable the integration of Google Wallet™ within theapplication, the Android® Software Development Kit (SDK) offers thefollowing three basic APIs: Google Wallet online commerce API, GoogleWallet for digital goods API, and Google Checkout API.

FIG. 2 illustrates an embodiment of a Process 200 for recharging a tollaccount using a virtual wallet. In various embodiments, Process 200 isperformed by an application, such as Application 121 described withrespect to FIG. 1A. In some embodiments, Process 200 is performed at 106of Process 100 described with respect to FIG. 1B. In one exemplaryembodiment shown in FIG. 2, Process 200 can be performed by theapplication to recharge a toll account using payment informationobtained directly from Google Wallet™. In various embodiments, theapplication is configured to exchange payment information with theGoogle Wallet™ backend server. In various embodiments, the applicationand the Google Wallet™ backend server exchange payment information usingsigned JavaScript Object Notation (JSON) data objects called JSON WebTokens (JWTs).

In some embodiments, the application can offer users the option torecharge their prepaid toll account using Google Wallet™.Advantageously, in some embodiments, using a virtual wallet such asGoogle Wallet™ further expedites the recharging process since users areable to avoid manually inputting payment information (e.g., credit cardnumber, billing address, etc.). For example, in some embodiments, aftera user, Bob, indicates that he would like to recharge his prepaid tollaccount by adding $10 to the account, he can then select or click on a“Buy with Google” button to complete or finalize the rechargingtransaction almost instantaneously. In some embodiments, selecting topay with a virtual wallet such as by clicking on the “Buy with Google”button triggers Process 200.

At 202, masked wallet information is requested. In various embodiments,the application sends to the Google Wallet™ backend server a maskedwallet request JWT. In various embodiments, masked wallet informationcomprises a Java object containing a masked or partially hidden versionof Bob's credit card number. In some embodiments, masked walletinformation can further include Bob's shipping address. At 204, a maskedwallet object is received. In various embodiments, in response to therequest from the application, the Google Wallet™ backend server returnsto the application a masked wallet response JWT. In various embodiments,the application can display an order review page or screen to Bob basedon the masked wallet information. At 206, a full wallet is requested. Invarious embodiments, after receiving the masked wallet object at 204,the application will then need full wallet information to complete Bob'sorder. As such, in some embodiments, the application then sends to theGoogle Wallet™ backend server a full wallet request JWT. At 208, fullwallet information is received. In various embodiments, the GoogleWallet™ backend server responds to the request by providing a fullwallet response JWT to the application. In various embodiments, the fullwallet information includes details of a single-use virtual credit cardfor the transaction. At 210, the single-use virtual credit card istransmitted. In various embodiments, the application passes thesingle-use virtual credit card provided by Google Wallet™ in the fullwallet to a merchant server (e.g., Payment Processor Server 160described with respect to FIG. 1A). At 212, transaction status isreceived. In various embodiments, the merchant server processes thepayment and notifies the application of the status of the transaction(e.g., success or failure). Finally, at 214, a status notificationobject is transmitted. In various embodiments, based on the statusnotification from the merchant server (e.g., success or failure), theapplication then creates and sends a transaction status JWT to theGoogle Wallet™ backend server. In addition, in various embodiments, theapplication displays a confirmation screen informing Bob that $10 hasbeen added to his prepaid toll account.

Dual Frequency Transponder Data Links

PCT Application No. PCT/EP2012/001765, entitled “Method and Apparatusfor Providing and Managing Information Linked to RFID Data Storage Mediain a Network”, filed Apr. 25, 2012, which is incorporated herein byreference, describes the management of data that is linked to orotherwise associated with a RFID storage medium. The various embodimentsof the methods and systems described herein are directed toward using adual frequency transponder to manage and replenish a toll account. Inthe various embodiments described herein, the dual frequency transpondercan communicate with both a NFC-enabled device and a UHF RFID reader. Invarious embodiments, data stored on the dual frequency transponderlinks, corresponds, or otherwise provide access to a toll account. Thus,in various embodiments, both NFC-enabled devices (e.g., Android®smartphones) and UHF RFID readers (e.g., common types of toll readers)are able to read or scan information that is stored on the dualfrequency transponder and then perform a number of essential functionsbased on this information.

As described earlier with respect to FIG. 1A, various embodiments of thesystems and methods enable an account to be managed and rechargedinstantly and on-the-spot. In various embodiments, bringing anNFC-enabled device (e.g., Device 120) within the range of a dualfrequency transponder (e.g., Transponder 110) automatically triggers thelaunch of an application on the NFC-enabled device. In variousembodiments, the application can provide the latest prepaid toll accountinformation (e.g., status, balance). Furthermore, in variousembodiments, the application is integrated with a virtual wallet (e.g.,Google Wallet™) thereby enabling a user to recharge the toll accountinstantly and on-the-spot. In the example described with respect to FIG.2, Bob uses his Android® smartphone to scan the dual frequencytransponder and is subsequently able to add $10 to his prepaid tollaccount.

In various embodiments, the information stored in the dual frequencytransponder links, corresponds, or otherwise provides access to anaccount. In various embodiments, a NFC-enabled device reads data that isstored on an RFID data storage medium (e.g., a dual frequencytransponder) and then uses this data to access additional data that isstored at a remote server. For example, in various embodiments, readingor scanning the information stored in the dual frequency transponderenables the application to access a designated memory area at a remoteserver (e.g., ETC Server 170). In some embodiments, the application isthen able to retrieve, for example, prepaid toll account informationfrom the remote server. Additionally, in various embodiments, theapplication is also able to update the toll account information storedat the remote server, including but not limited to by submitting arecharge payment that alters the status or balance of the toll account.

FIG. 3 illustrates an embodiment of a System 300 in which an account ismanaged. In various embodiments, User 32 operates Device 10, which is aNFC-enabled device such as an Android® smartphone. In variousembodiments, Application 30 is an application that permits User 32 tomanage and replenish a toll account, including by providing currentaccount information (e.g., status, balance) and options to replenish thetoll account. In various embodiments, Device 10 includes a NFC RFIDReader 8 that is capable of reading data stored in RFID Storage Medium4. In various embodiments, RFID Storage Medium 4 is a dual frequencytransponder such as Transponder 110 described with respect to FIG. 1A orTransponder 400 described with respect to FIG. 4. In some embodiments,Application 30 is installed on Device 10. As such, in some embodiments,when NFC RFID Reader 8 reads or scans data from RFID Storage Medium 4,Device 10 can launch Application 30 automatically based on this data.Otherwise stated, in some embodiments, Application 130 can be launchedwhen User 32 brings Device 10 within sufficient range of RFID StorageMedium 4 for NEC RFID Reader 8 to read or scan data from RFID StorageMedium 4. In other embodiments, Application 130 is not already installedon Device 10. In those embodiments, data read or scanned from RFIDStorage Medium 4 directs Device 10 to a link to download and installApplication 130.

As shown in FIG. 3, in various embodiments, RFID Storage Medium 4includes a RFID Data Record 24 and an additional Memory 34. In variousembodiments, NFC RFID Reader 8 is configured to read or scan the datastored on RFID Data Record 24. For example, in some embodiments, NFCRFID Reader 8 directs a request to RFID Storage Medium 4. In response,in some embodiments, RFID Storage Medium 4 releases the data stored onRFID Data Record 24 to NFC RFID Reader 8. In some embodiments, User 32must be authenticated (e.g., biometrics, username, password) before RFIDStorage Medium 4 releases its data to NFC RFID Reader 8. In variousembodiments, Application 30 generates uses the data released from RFIDData Record 24 to generate access rights for Additional Data 22 thatstored in Data Memory Area 20 of a Remote Server 18. In someembodiments, in order to generate access rights to Additional Data 22,User 32 also must provide one or more forms of security orauthentication credentials (e.g., biometrics, username, password). Invarious embodiments, Additional Data 22 can include account information(e.g., status, balance) with respect to the toll account. In someembodiments, Remote Server 18 can be a server associated with an ETCsystem, such as ETC Server 170 described with respect to FIG. 1A. Invarious embodiments, Application 30 requests for Additional Data 22 fromRemote Server 18 by sending, for example, access rights to Remote Server18 over Network 16. In various embodiments, in response to the requestfrom Application 30, Remote Server 18 transmits Additional Data 22 toDevice 10 via Network 16. In various embodiments, Application 30 canthen provide, with or without further processing or analysis, AdditionalData 22 to User 32.

Dual Frequency Transponder

FIG. 4 illustrates an embodiment of a Transponder 400 used to manage anaccount. In various embodiments, Transponder 400 is a multi-frequency orfrequency-independent transponder. In various embodiments, Transponder400 is a dual frequency transponder that operates over both the HF(e.g., 13.56 MHz) and UHF (e.g., 865-928 MHz) band. In variousembodiments, Transponder 400 shown in FIG. 4 can be used to implementTransponder 110 described with respect to FIG. 1A. Advantageously, invarious embodiments, Transponder 400 is capable of communicating withboth a NFC-enabled device and a UHF RFID reader. For instance, in someembodiments, when a NFC-enabled device such as an Android® smartphone isbrought within the range of Transponder 400, the NFC-enabled device canrespond by automatically launching an application (e.g., Application 121described with respect to FIG. 1A) that enables a quick and on-the-spotrecharge of a toll account. In addition, in some embodiments, a UHF RFIDreader installed at a toll gate can use information scanned fromTransponder 400 to determine the correct prepaid toll account from whichto deduct a toll charge.

As FIG. 4 shows, Transponder 400 includes a base layer and at least oneradio frequency device disposed upon the base layer. In variousembodiments, the radio frequency device comprises at least one chip andat least one antenna that are in electrically coupled with the chip. Insome embodiments, Transponder 400 can include a frequency-independentchip. In those embodiments, Transponder 400 can include a singlemanufactured silicon chip that is configured, through proper connectionsand match to an appropriate antenna, to operate using any of therelevant frequencies (e.g., 13.56 MHz and 915 MHz) assigned toTransponder 400. Alternately, in some embodiments, Transponder 400 caninclude a multi-frequency (e.g., dual frequency) chip. In thoseembodiments, Transponder 400 includes a chip that is designed andcharacterized to operate with a specific antenna at several (e.g., two)different frequencies.

As FIG. 4 shows, in some embodiments, Transponder 400 further includesan Analog Control Unit 410, which is a dual interface with a combinationof two frequencies. For example, in some embodiment, Analog Control Unit410 includes a HF System 411 and a UHF System 412, both described inmore detail below. In various embodiments, UHF System 412 operates overthe 915 MHz band and is used for communicating with UHF RFID readers,including but not limited to conventional UHF RFID toll readers. As FIG.4 further shows, in some embodiment, UHF System 412 includes Antenna413, which can be a dipole antenna. Meanwhile, in various embodiments,HF System 411 is used for communicating with NFC-enabled devices, suchas Android® smartphones. In some embodiments, the HF System 411 includesAntenna 414, which can be a coil antenna constructed from a helix ofinsulated wire.

In various embodiments, Transponder 400 can further include DigitalControl Unit 420 and Memory 430. In various embodiments, Analog ControlUnit 401 comprises a continuous-time system. That is, in variousembodiments, Analog Control Unit 401 comprises a system that iscontinuous in both time and magnitude. Furthermore, in variousembodiments, Analog Control Unit 401 inputs and outputs analog signals.A signal is considered analog if it is defined for every point in time(i.e., continuous-time) and is able to take any real magnitude valuewithin its range. In contrast, in various embodiments, Digital ControlUnit 420 comprises a discrete-time and quantized system. In variousembodiments, Digital Control Unit 420 takes in digital input signals andproduces digital output signals. A digital signal is only defined forparticular points in time (i.e., discrete-time) and can only take oncertain quantized values (e.g., 0s and 1s in a binary system). In someembodiments, Analog Control Unit 410, Digital Control Unit 420, andMemory 430 are all components on a single integrated RFID circuit chip.

FIG. 5 illustrates an embodiment of an UHF System 500. In variousembodiments, UHF System 500 can be used to implement UHF System 412described with respect to FIG. 4. Furthermore, in various embodiments,UHF System 500 can be used to implement the UHF component of a dualfrequency transponder, such as Transponder 110 described with respect toFIG. 1A. In various embodiments, UHF System 500 operates over a UHF(865-928 MHz) band. As shown in FIG. 5, UHF System 500 uses the 915 MHzor 2.45 GHz band. In various embodiments, a dual frequency transponderthat incorporates UHF System 500 is capable is interacting with a UHFRFID reader. Many ETC systems have UHF RFID readers installed at tollgates. For instance, readers in the E-ZPass® system broadcast a 915 MHzsignal while E-ZPass® transponders are configured to listen for andrespond to the 915 MHz signal. In some cases, particularly where atransponder is configured to operate passively, the transponder canrespond to the 915 MHz signal broadcast by a reader with a backscattersignal to the reader that conveys the data stored in the transponder. Invarious embodiments, data transmitted to the UHF RFID reader includesdata (e.g., a unique radio signature) that links, corresponds, orotherwise provides access to the toll account associated with eachpassing vehicle. As such, in various embodiments, this data enables theETC system to identify or determine the toll account to which to applythe toll charge.

As shown in FIG. 5, UHF System 500 includes AC/DC Converter 510, PowerSupply Control Unit 520, Instruction Sequencer 530, and Memory 540. Invarious embodiments, AC/DC Converter 510 receives an alternating current(AC) and converts it to a direct current (DC). Meanwhile, in variousembodiments, Power Supply Control Unit 520 is configured to regulatevoltage and current to protect UHF System 500 fluctuations in power(e.g., power surge). In various embodiments, Instruction Sequencer 530queues instructions that are directed to Memory 540. Finally, in variousembodiments, Memory 540 comprises an EEPROM (Electrically ErasableProgrammable Read-Only Memory) that stores data, such as instructionsfrom Instruction Sequencer 530.

FIG. 6 illustrates an embodiment of a HF System 600. In variousembodiments, HF System 600 can be used to implement HF System 411described with respect to FIG. 4. Furthermore, in various embodiments,HF System 600 can be used to implement the HF component of a dualfrequency transponder, such as Transponder 110 described with respect toFIG. 1A. As shown in FIG. 6, HF System 600 uses the 13.56 MHz band. Invarious embodiments, a dual frequency transponder that incorporates HFSystem 600 is capable of interacting with a NFC-enabled device (e.g.,Android® smartphone) when the dual frequency transponder touches, taps,or is otherwise brought within the range of the NFC-enabled device. Forexample, bringing an Android® smartphone within the range of the dualfrequency transponder activates an Android Beam™ feature on thesmartphone.

The Android Beam™ feature allows data to be transferred one NFC-enableddevice to another NFC-enabled device via NFC. For example, in someembodiments, Android Beam™ allows data to be transferred from the dualfrequency transponder to an Android® smartphone via NFC. In variousembodiments, data from the dual frequency transponder triggers thelaunch of an appropriate application on the Android® smartphone tohandle the data. In various embodiments of the systems and methodsdescribed herein, when a NFC-enabled device (e.g., Android® smartphone)reads data from a dual frequency transponder with an integrated HFcomponent (e.g., HF System 600), an application to recharge a tollaccount launches automatically. For example, in some embodiments, dataread from the dual frequency transponder links, corresponds, orotherwise provide access to a toll account. In one common scenario, thetoll account has a deficient balance and needs to be recharged before acorresponding vehicle can pass through an ETC toll gate. In variousembodiments, the application, through integration with a virtual wallet(e.g., Google Wallet™), enables the toll account to be rechargedinstantly and on-the-spot.

As shown in FIG. 6, HF System 600 includes Modulator 610, AC/DCConverter 612, Codifier 614, Decoder 616, Power Supply Control Unit 618,Instruction Sequencer 620, Security Administrator 622, CryptographicBlock 624, and Memory 626. In various embodiments, Modulator 610 isconfigured to receive baseband signals from an antenna, such as coilAntenna 414 described with respect to FIG. 4. In various embodiments,AC/DC converter 612 is configured to receive and convert an alternatingcurrent (AC) to a direct current (DC). Meanwhile, in variousembodiments, Codifier 614 is configured to encode the baseband signalsreceived by Modulator 610 so that the signals can be utilized by anotherdevice or protocol, including Instruction Sequencer 620. In variousembodiments, Decoder 616 is configured to decode information fromCodifier 614 so that it may be used by another device or display. Invarious embodiments, Instruction Sequencer 620 is configured to queueinstructions destined for Memory 626. In various embodiments, SecurityAdministrator 622 is configured to validate the cryptographic keys sentto Cryptographic Block 624. In various embodiments, Cryptographic Block624 or Memory 626 can be configured store the security keys that, forexample, have been validated by Security Administrator 622 and that canbe used to control (e.g., grant, deny) access to the dual frequencytransponder's memory or certain content therein. Finally, in variousembodiments, Power Supply Control Unit 618 is configured to regulatevoltage and current in order to protect HF System 600 from powerfluctuations (e.g., power surges).

RFID-Enabled License Plate

The various embodiments of the systems and methods described herein aredirected toward the use of a dual frequency transponder (e.g.,Transponder 110 described with respect to FIG. 1A and Transponder 400described with respect to FIG. 4) to manage and recharge an account. Inparticular, in various embodiments, the dual frequency transponderprovides information that enables the application of both toll chargesand reload payments to the appropriate prepaid toll account. Since invarious embodiments, the dual frequency transponder is configured tointeract both with the UHF RFID toll readers and with a user'sNFC-enabled device, the dual frequency transponder should preferably beset in a location that is convenient and accessible for scanning by boththe UHF RFID toll readers and the user's NFC-enabled device. Thus, insome embodiments, it is desirable to attach the dual frequencytransponder to the vehicle associated with the toll account. As such, insome embodiments, the dual frequency transponder can be a sticker (e.g.,a self-adhesive decal that can be placed on an automobile window,windshield, or license plate), a clamshell card, or an encapsulateddevice (e.g., in the housing of a rear-view mirror, headlights ortaillights, the vehicle's front or rear bumpers, or in anynon-conductive component of the vehicle).

In some embodiments, the dual frequency transponder can also be embeddedin the vehicle's license plate. However, vehicle license plates are mostcommonly made from metal (e.g., aluminum). Direct and uninsulatedcontact between a transponder (single or multi-frequency) and a metallicense plate (e.g., applying the transponder directly onto the metallicense plate) can short or severely detune the transponder's antenna(s)(e.g., Antenna 413 and Antenna 414 described with respect to FIG. 4),rendering the transponder virtually unreadable. Thus, in the exemplaryembodiments described in more detail below, a transponder is embedded ina metal license plate in ways that neither compromise the performance ofthe transponder's antenna(s) nor add undesirable bulk to the licenseplate's usual dimensions. In the various exemplary embodiments describedin more detail below, a RFID-enabled license plate is configured toresonate at multiple frequencies (e.g., HF and UHF bands). In someembodiments, a resonator for the transponder is formed from the licenseplate itself if the license plate is metal. In other embodiments,whether the plate is metal or non-metal, the resonator can also beformed from a metalized layer (e.g., retro-reflective material,holographic foil, or any other appropriate metallic substrate) coveringthe license plate.

FIG. 7A illustrates the top view of an embodiment of a RFID-EnabledLicense Plate 700. In various embodiments, RFID-Enabled License Plate700 includes a metal Plate 710. In various embodiments, RFID-EnabledLicense Plate 700 can be configured to include one or more slots, whichare open areas that are cut or punched out of Plate 710. In someembodiments, RFID-Enabled License Plate 700 can be configured to includemultiple slots. As shown in FIG. 7A, in some embodiments, RFID-EnabledLicense Plate 700 includes Slot 720 and Slot 730. In variousembodiments, both Slot 720 and Slot 730 can be filled with a non-metalmaterial. In various embodiments, the non-metal material can be stuffed,extruded, or otherwise deposited into Slot 720 and Slot 730. In variousembodiments, the non-metal material remains flush with respect to boththe front and rear surfaces of Plate 710. Furthermore, as shown in FIG.7A, a RFID Strap 740 can be positioned across Slot 730 as illustrated.In some embodiments, RFID Strap 740 includes a RFID chip as well ascontacts that are connected to or capacitively coupled with Plate 710.In other embodiments, RFID Strap 740 can include a RFID chip and anantenna, wherein the antenna is inductively coupled with Plate 710. Invarious embodiments, the respective and relative dimensions, spacing,and location of Slots 720 and 730 are configured such that the slotantenna formed from Plate 710, Slots 720 and 730, and Strap 740 willresonate at multiple desired frequencies. In various embodiments, theslot antenna configured according to FIG. 7A is able to resonate at botha HF (e.g., 13.56 MHz) and a UHF (e.g., 915 MHz) band. As described inmore detail below, in other embodiments, instead of multiple slots(e.g., Slot 720 and Slot 730 in Plate 710) configured to resonate atseveral different frequencies, a RFID-enabled license plate can alsoinclude just a single slot configured to resonate at a single frequency.

FIG. 7B illustrates the top view of another embodiment of anRFID-Enabled License Plate 700. In various embodiments, RFID-EnabledLicense Plate 700 includes a Plate 710 that is constructed out of metal.As shown in FIG. 7B, in various embodiments, RFID-Enabled License Plate700 can be configured to include a single Slot 720, which is cut orpunched out of Plate 710. In various embodiments, Slot 720 can bestuffed, extruded, or otherwise deposited with a non-metal material thatremains flush with respect to both the front and rear surfaces of Plate710. In the embodiment shown in FIG. 7B, an RFID Strap 730 is positionedover Slot 720. In various embodiments, RFID Strap 730 includes a RFIDChip 740 and Contacts 750. In various embodiments, Contacts 750 can beconnected to Plate 710 through solder, adhesive paste, or both. In someembodiments, Contacts 750 are capacitively coupled with Plate 710.Depending on the embodiment, RFID Strap 730 can be placed on either thefront surface or the rear surface of Plate 710. Configured according toFIG. 7B, the entire Plate 710 becomes a slot antenna coupled with theRFID Chip 740, which is less sensitive to the detuning effects of ametal car frame.

FIG. 7C illustrates the top view of another embodiment of RFID-EnabledLicense Plate 700. In various embodiments, RFID-Enabled License Plate700 comprises a metal Plate 710 that includes a Slot 720, which is anopen area that has been cut or punched out of Plate 710. In someembodiments, instead of an RFID strap (e.g., RFID Strap 740 describedwith respect to FIGS. 7A and 7B) positioned over Slot 720, an RFIDTransponder Module 730 is placed directly inside of Slot 720 as shown inFIG. 7C. In various embodiments, RFID Transponder Module 730 includes anRFID Chip 740 that is coupled with a Feeding Loop 750. Furthermore, asshown in FIG. 7C, in some embodiments, Slot 720 is positioned such thatFeeding Loop 750 is either capacitively coupled with Plate 710. Althoughnot shown, in other embodiments, Feeding Loop 750 can be inductivelycoupled with Plate 710. Advantageously, RFID Transponder Module 730 canbe made sufficiently thin such that even when RFID Transponder 730 isinstalled within Slot 720, it creates a substantially planar surfacewith respect to Plate 710.

In some embodiments, a RFID-enabled license plate can include atransponder that will not function absent a valid and properlypositioned vehicle registration sticker. For example, in someembodiments, the transponder can be intentionally tuned to a lowerfrequency (e.g., less than 915 MHz) and therefore cannot be properlyread by a UHF RFID reader. Meanwhile, in some embodiments, applying avalid vehicle registration sticker in the correct position on theRFID-enabled license plate tunes the transponder to the correct andoperational frequency (e.g., 915 MHz) so that the transponder can beread by a UHF RFID reader. In various embodiments, the vehicleregistration sticker is fabricated from or otherwise includes one ormore metallic or other conductive materials.

FIG. 8 illustrates an embodiment of a RFID-Enabled License Plate 800. Invarious embodiments, RFID-Enabled License Plate 800 includes a metalPlate 810 and a RFID Module 820. As shown in FIG. 8, RFID-EnabledLicense Plate 800 comprises an RFID Booster 830. In some embodiments,RFID Booster 830 can be a slot antenna formed from Plate 810, RFIDModule 820, and one or more properly sized and positioned slots in Plate810. In various embodiments, RFID Module 820 is intentionally tuned to alower, inoperable frequency. In various embodiments, a valid VehicleRegistration Sticker 840 must be applied in a proper location on Plate810 in order for RFID Module 820 to function properly (e.g., to bescanned or read by a UHF RFID toll reader). As will be described in moredetail below, applying Vehicle Registration Sticker 840 in the correctlocation on RFID-Enabled License Plate 800 tunes RFID Module 820 to theproper frequency band.

FIG. 9 illustrates an embodiment of Vehicle Registration Sticker 900which is used in conjunction with RFID-Enabled License Plate 800 asdescribed in FIG. 8. In various embodiments, Vehicle RegistrationSticker 900 can be used to implement Vehicle Registration Sticker 840described with respect to FIG. 8. As shown in FIG. 9, the back ofVehicle Registration Sticker 900 includes a Loop 910. In variousembodiments, when Vehicle Registration Sticker 900 is affixed to aRFID-enabled license plate (e.g., RFID-Enabled License Plate 800) in aproper location, Loop 910 couples to a RFID transponder and tunes theRFID transponder to the proper frequency band for operation. In otherembodiments, Vehicle Registration Sticker 900 can comprise RFID Module820 (i.e., a chip and an antenna). In those embodiments, placement ofthe Vehicle Registration Sticker on RFID-Enabled License Plate 800couples Vehicle Registration Sticker 900 with RFID Booster 830. Forexample, in some embodiments, Vehicle Registration Sticker 900 caninclude a single frequency (e.g., HF or NFC) transponder. Although FIG.8 shows that Vehicle Registration Sticker 900 is placed directly overRFID Module 820, in embodiments where Vehicle Registration Sticker 900is composed of or otherwise includes conductive material, RFID Module820 do not have to be directly underneath Vehicle Registration Sticker900.

Typically, in the United States, motorists are required to renew theirvehicle registration on an annual basis. For example, California licenseplates have a month and a year sticker. A properly registered vehicle inCalifornia will have been issued a sticker that shows the current year.Although the registration status of a vehicle can be verified visually,in many instances, it would be preferable to verify vehicle registrationstatus through electronic and automated means. Thus, in variousembodiments, a vehicle registration sticker that is used in conjunctionwith a RFID-enabled license plate can further include or be constructedout of a material that gradually degrades as the vehicle's registrationapproaches expiration. In this manner, an up-to-date vehicleregistration sticker is able to tune a RFID transponder in theRFID-enabled license plate to the proper frequency while an expiredvehicle registration sticker cannot. Consequently, a vehicle cannotsuccessfully pass through a checkpoint unless the vehicle is alsoproperly registered and is displaying a current vehicle registrationsticker.

Vehicle registration stickers are very often made out of a metallicmaterial (e.g., retro-reflective foil). Therefore, in some embodiments,the vehicle registration sticker can be made out of a retro-reflectivematerial that degrades over time. In another embodiment, the loop on theback of the vehicle registration sticker can be made out of a materialthat degrades over time. Finally, in some embodiments, the adhesive usedto bond the vehicle registration sticker to a RFID-enabled license platecan degrade over time.

In various embodiments where a RFID-enabled license plate (e.g.,RFID-Enabled License Plate 700 and 800) comprises a dual frequencytransponder (e.g., Transponder 110, Transponder 400), the RFID-Enabledlicense plate is able to communicate with a NFC-enabled device and witha UHF RFID reader device. In particular, in various embodiments, theRFID-enabled license plate is designed to be read as a vehicle passesthrough a toll gate. In various embodiments where the dual frequencytransponder is embedded, integrated, or otherwise included in thevehicle's license plate, it would be preferable to install or place thetoll readers in the road, rather than in overhead gantries as inconventional ETC systems. FIG. 10 illustrates an embodiment of theplacement of a Reader 1000 with respect to a RFID-enabled license plate.Advantageously, placing toll readers according FIG. 10 can actuallygreatly reduce the cost of infrastructure associated with ETC since iteliminates the need to build and install gantries above the road. Invarious embodiments, the maximum height from which a transponder can beread is approximately 3.5 feet above the surface of the pavement.Meanwhile, in various embodiments, Reader 1000 is embedded at least 4inches below the surface of the pavement. Suppose for commonapplications such as electronic toll collection, the transponder in aRFID-enabled license plate needs to include a 192-bit Tag Identification(TID) memory. As such, in various embodiments, the maximum speed atwhich Reader 1000 can successfully read a dual frequency transponderwith a 192-bit TID memory that is embedded in a license plate attachedto a passing vehicle is 140 kilometers or 87 miles per hour.

FIG. 11 illustrates an embodiment of a universal transponder 1100.Referring to FIG. 11, in various embodiments, the universal transponder1100 can provide multiple functionalities including, for example, butnot limited to, short range connectivity (e.g., NFC, Bluetooth®) withanother device (e.g., smartphone), camera, credit card reader (e.g.,Square®), audio speaker, and remote control (e.g., garage door opener).In various embodiments, the universal transponder 1100 can have a metalcasing that can act as an antenna (e.g., in the UHF band). According toone exemplary embodiment, the universal transponder is able to interfacewith both NFC/HF and UHF systems, and can be used to manage an account.

What is claimed:
 1. A system comprising: a wearable mobile devicecomprising a metal casing and a radio frequency identification (RFID)tag having a transponder, the transponder comprising a plurality ofantennas, wherein the metal casing comprises a body casing and whereinthe body casing is at least one of the plurality of antennas, thetransponder configured to: communicate via the plurality of antennas andcorresponding plurality of frequencies, and store information related toan account of a user of the wearable mobile device, wherein the RFID tagis configured to: communicate at least a first portion of theinformation related to the account and stored on the RFID tag to a firstdevice using a first RFID reader included the first device operating ata first frequency of the plurality of frequencies, and communicate atleast a second portion of the information related to the account andstored on the RFID tag to a second device using a second RFID readerincluded the second device operating at a second frequency of theplurality of frequencies, wherein the first device is configured tolaunch an application in response to receiving the at least the firstportion of the information read from the RFID tag, the applicationcomprising a plurality of instructions stored on a memory of the firstdevice, the plurality of instructions causing a processor of the firstdevice to access the account based on the first portion of theinformation related to the account and update an account balance of theaccount through interactions with a virtual wallet, and wherein thesecond device is configured to apply a charge to the account based, inpart, on the at least a second portion of the information related to theaccount.
 2. The system of claim 1, wherein the first device is a mobiledevice configured to: read, using the first RFID reader, the firstportion of the information related to the user stored on the RFID tag,and perform one or more actions based, in part, on the first portion ofthe information read from the RFID tag.
 3. The system of claim 2,wherein the first device is further configured to: update the accountinformation by updating an account status comprised in the accountinformation based on one or more instructions received from a user viathe first device.
 4. The system of claim 1, wherein, based in part oncommunicating at least one of the first portion or second portion of theinformation related to the account, prompt a user to provide one or moreforms of authentication credentials.
 5. The system of claim 4, whereinthe wearable mobile device is configured to: prompt a user to provideone or more forms of authentication credentials, and communicate therest of the information stored on the RFID tag based on successfullyauthenticating the provided one or more forms of authenticationcredentials.
 6. The system of claim 4, wherein the first device isconfigured to: prompt a user to provide one or more forms ofauthentication credentials, and access the rest of the informationstored on the RFID tag based on successfully authenticating the providedone or more forms of authentication credentials.
 7. The system of claim1, wherein the second device is configured perform an action related tothe account based, in part, on the second portion of the informationrelated to the account from the RFID tag.
 8. The system of claim 1,wherein the wearable mobile device is a watch comprising a computingdevice.
 9. The system of claim 1, wherein the first frequency comprisesone or more of a high frequency (HF) or an ultra-high frequency (UHF).10. The system of claim 1, wherein the metal casing is configured tocommunicate via a second antenna and the second frequency, wherein thesecond frequency comprises an ultra-high frequency.
 11. The system ofclaim 1, wherein the at least a first portion of the information relatedto the account identifies or links to account information of the accountstored in a remote server.
 12. A mobile device comprising: a metalcasing; and a radio frequency identification (RFID) tag having atransponder comprising a plurality of antennas, wherein the metal casingcomprises a body casing and wherein the body casing is at least one ofthe plurality of antennas is at least one of the plurality of antennas,the transponder configured to: communicate via the plurality of antennasand corresponding plurality of frequencies, and store informationrelated to an account of a user of the mobile device, wherein the RFIDtag is configured to: communicate at least a first portion of therelated to the account and stored on the RFID tag to a first deviceusing a first RFID reader included the first device operating at a firstfrequency of the plurality of frequencies, and communicate at least asecond portion of the information related to the account and stored onthe RFID tag to a second device using a second RFID reader included thesecond device operating at a second frequency of the plurality offrequencies, and wherein the mobile device is a wearable mobile device,wherein the first device is configured to launch an application inresponse to receiving the at least the first portion of the informationread from the RFID tag, the application comprising a plurality ofinstructions stored on a memory of the first device, the plurality ofinstructions causing a processor of the first device to access theaccount based on the first portion of the information related to theaccount and update an account balance of the account throughinteractions with a virtual wallet, and wherein the second device isconfigured to apply a charge to the account based, in part, on the atleast a second portion of the information related to the account. 13.The mobile device of claim 12, wherein the wearable mobile device is awatch comprising a computing device.
 14. The mobile device of claim 12,wherein the first frequency comprises one or more of a high frequency(HF) or an ultra-high frequency (UHF).
 15. The mobile device of claim12, wherein the metal casing is configured to communicate via a secondantenna and the second frequency, wherein the second frequency comprisesan ultra-high frequency.
 16. The mobile device of claim 12, wherein,based in part on communicating at least one of the first portion orsecond portion of the information related to the account, prompt a userto provide one or more forms of authentication credentials.
 17. Themobile device of claim 16, wherein the mobile device is configured to:prompt a user to provide one or more forms of authenticationcredentials, and communicate the rest of the information stored on theRFID tag based on successfully authenticating the provided one or moreforms of authentication credentials.
 18. The mobile device of claim 12,wherein the mobile device comprises the functionality of one or more ofa camera, credit card reader, audio speaker, or remote controller.